WEBVTT

00:06.960 --> 00:09.320
Hello, guys, and welcome to another video

00:09.350 --> 00:12.800
for this chapter
in this video, we are going to give short

00:12.830 --> 00:16.520
light on the Christmas tree Attack. A
Christmas tree.

00:16.540 --> 00:21.920
Attack sent a large number of specially
crafted TCP packets to incentivize and has

00:21.950 --> 00:25.740
all the options set so that
any protocol can be used.

00:25.760 --> 00:28.040
The name is derived from the idea that all

00:28.070 --> 00:31.380
the settings are turned
to on within the packet.

00:31.400 --> 00:34.220
So it is lit up like a Christmas tree.

00:34.250 --> 00:39.900
Christmas tree packets are also known as
kamikaze packets and lab test segments.

00:39.930 --> 00:42.320
Christmas tree attacks require much more

00:42.350 --> 00:48.060
processing by routers and
devices than other packets.

00:48.090 --> 00:50.220
Not numbers of these packets

00:50.250 --> 00:55.280
can use so much processing power that it
ties up this device is effectively making

00:55.310 --> 01:01.340
any other task nearly impossible, thus
denying service to legitimate traffic.

01:01.370 --> 01:03.400
Receiving these types of packets is not

01:03.430 --> 01:07.050
usable and therefore should
be regarded as suspicious.

01:07.080 --> 01:08.080
Intrusion Detection

01:08.110 --> 01:12.490
System can detec this packet
as to some firewalls.

01:12.520 --> 01:15.740
The TCP packet contains many flags,

01:15.770 --> 01:23.060
synchronization, acknowledgement, fin
flag reset, urgent pointer and push.

01:23.090 --> 01:28.700
Out of all these flags in the Christmas
tree, Attack especially crafted TCP Packet

01:28.730 --> 01:35.180
were urgent puch and Fin flags stand
down are sent in a normal situation.

01:35.210 --> 01:38.360
This combination of these flags.

01:38.880 --> 01:40.880
Out of all these flags in a Christmas

01:40.910 --> 01:46.930
tree, Attack especially grafted TCP packet
were urgent push and flags stand down.

01:46.960 --> 01:49.720
In a normal situation.

01:49.750 --> 01:51.920
The combination of these flags with bits

01:51.950 --> 01:56.480
stand on is not sent
upon sending such packets.

01:56.510 --> 02:00.200
The target devices may
respond differently.

02:00.480 --> 02:02.960
As different operating systems may react

02:02.990 --> 02:07.780
differently, it can be used for operating
system, fingerprinting port

02:07.810 --> 02:13.280
state and other information,
once it gets the information, you can look

02:13.310 --> 02:17.960
for potential loopholes and
vulnerabilities in the network.

02:18.120 --> 02:21.720
So as you can see from this photo
presented in the slide, when you are

02:21.750 --> 02:26.730
looking into the packets themselves,
you can see

02:26.760 --> 02:32.340
if this combination of bits turned
on and off right inside each packet.

02:32.370 --> 02:36.360
We're going to explore and see this
practically while we are performing an

02:36.390 --> 02:43.080
Attack and capturing the traffic
on our packet machine.

02:43.200 --> 02:46.040
We can write some custom code that craft

02:46.070 --> 02:50.140
the required packet
to perform certain Attack.

02:50.170 --> 02:58.040
And the code will look something like
this code presented on this slide.

02:58.480 --> 03:04.640
We can also use the hping3 command and the
command structure will be looking

03:04.670 --> 03:11.080
something like I have on this slide
now we will analyze this Attack using the

03:11.110 --> 03:16.360
popular nmap scan and capture the traffic,
as we said, with Wireshark on our target

03:16.390 --> 03:21.740
machine and see with our own
eyes, how the packet looks like.

03:21.770 --> 03:24.520
So we are in our Linux machine, which is

03:24.550 --> 03:28.940
going to be the Attack machine, and we are
ready to type the

03:28.970 --> 03:34.460
nmap command and use the appropriate
flags for the Christmas tree Attack.

03:34.490 --> 03:41.380
And we are going to attack the
Windows system that I have in my lap.

03:41.410 --> 03:45.220
So let's go ahead and
type the Nmap command.

03:45.250 --> 03:48.200
We are going to use the

03:48.640 --> 03:53.580
Christmas tree flag for nmap,
which is dash small s capital X.

03:53.610 --> 03:58.040
Small s capital X and then we type the IP

03:58.070 --> 04:06.940
of the Attack of the target machine,
which in this case is my Windows system.

04:06.970 --> 04:09.360
Before you present and perform the Attack,

04:09.390 --> 04:15.320
remember to go into your windows machine
open Wireshark, select the network you

04:15.350 --> 04:19.340
want to capture the traffic from and start
capturing the packet

04:19.360 --> 04:26.120
so in a in my Windows system in my lap, I
have already opened the Wireshark and it's

04:26.150 --> 04:31.120
capturing the traffic already and we can
now just go ahead and press, enter and

04:31.150 --> 04:35.420
perform the Attack on our
local windows system.

04:35.450 --> 04:36.860
So when the Attack

04:36.890 --> 04:43.480
will finish, we are going straight to our
Windows system and stop the

04:43.520 --> 04:49.500
traffic capture and we can investigate
all the packets going there.

04:49.530 --> 04:54.680
So as you can see, the Nmap
Christmas tree Scan stopped.

04:54.710 --> 04:56.980
So let's go to our Windows machine,

04:57.010 --> 05:00.300
stop the capture and see
what's going on there.

05:00.330 --> 05:04.820
So I stopped the network up
to now in our Windows system.

05:04.840 --> 05:08.180
And we can go through all the packets

05:08.210 --> 05:14.280
and find the packages are part
of the Christmas tree Attack.

05:30.880 --> 05:33.580
If you're doing this by, it is

05:33.600 --> 05:38.940
practically impossible to see
these type of Attack

05:38.970 --> 05:43.700
with all the other normal traffic that is
going through your network,

05:43.730 --> 05:53.020
which makes it very important to have this
intrusion prevention systems that were.

05:53.040 --> 05:55.160
When someone is performing certain Attack,

05:55.190 --> 05:59.760
you will be able to see
the alarm immediately.

06:16.000 --> 06:18.380
So why don't you spot the

06:18.410 --> 06:27.500
Christmas tree, packets you can see
that they are all going together.

06:27.530 --> 06:34.640
And they're starting from a specific port
on our attacking machine, and it's

06:34.670 --> 06:40.600
automizing the set of ports
on our system, as you can see.

06:40.960 --> 06:48.020
So let's just choose one of those and go
through and check the flags,

06:48.040 --> 06:55.540
you can see that the flags are in the
transmission control protocol and.

06:55.570 --> 06:58.200
You can expand these.

06:58.400 --> 07:05.240
And see the fin psh urgent flags.

07:07.320 --> 07:14.260
So you can see the reserved not set
the echo not set said the urgent set

07:14.290 --> 07:23.240
push push set syn not set
is not set and fin is set.

07:23.280 --> 07:27.680
You can see that whatever
packet you choose.

07:27.840 --> 07:32.100
Well, this scan is being performed they

07:32.130 --> 07:41.620
look the same with the same with the
same set of combinations happening.

07:41.650 --> 07:43.460
As we mentioned earlier,

07:43.480 --> 07:48.400
these Attack is very easy to see if you
have an Intrusion Prevention System as

07:48.420 --> 07:53.240
these systems have signatures that are
specifically designed to identify

07:53.270 --> 07:58.100
Christmas tree attacks
when they are going through your network.

07:58.130 --> 08:02.560
There are also some
IP Tables rules if you're using a Linux

08:02.590 --> 08:10.460
system on your home or your work that
you can protect from these Attack.

08:10.480 --> 08:15.780
So as you see,
so as you see, there are a few IP tables,

08:15.800 --> 08:21.560
rules presented on the slide you can use
to protect your Linux system machine.

08:22.320 --> 08:28.620
And remember that Intrusion Prevention
System are very important and are the

08:28.650 --> 08:34.700
systems that you need to identify
properly the Christmas tree attacks.

08:34.730 --> 08:36.260
So that was it for this video.

08:36.290 --> 08:39.060
And now you can go ahead and
press on the next video.

08:39.080 --> 08:40.240
Where you are going to learn how to

08:40.270 --> 08:44.000
decrypt SSL and TLS
traffic using Wireshark.

